Consistent data retrieval in a multi-site computing infrastructure

ABSTRACT

Embodiments of the invention relate to dynamic application migration in a shared pool of configurable computer resources with disaster recovery support. Data from an application is replicated from local data storage to remote data storage. A consistency point of the data is created in both the local data storage and the remote data storage. The application may be migrated to a second data site with separate local data storage. The migration may be planned or unplanned. Based upon the created consistency point, a consistent set of application data may be requested to support a read operation from the migrated application.

BACKGROUND

This invention relates to dynamic application migration in a shared poolof configurable computing resources. More specifically, the inventionrelates to retrieval of a consistent dataset to support the applicationmigration.

Cloud computing is a model of service delivery for enabling convenient,on-demand network access to a shared pool of configurable computerresources, e.g. networks, network bandwidth, servers, processing,memory, storage, applications, virtual machines, and services, that canbe rapidly provisioned and released with minimal management effort orinteraction with a provider of service. One of the characteristics ofcloud computing infrastructure is that applications can be launched froma plurality of locations. Several factors drive the decision to launchan application in a specific data center, including resourceavailability, user location, disaster awareness, data location, andavailable facilities. However, the prior art cloud computingconfigurations do not provide flexibility of separation of the locationof the data from the application location.

On another level, it is known that the current cloud computing modelsare not flexible with respect to disaster recovery. More specifically,it is known in the art that a failed application must recover in adesignated recovery center. For example, the current models do notenable recovery based upon the factors listed above. At the same time,because current models require the entire data volume to be locatedlocal to the recovery site, the entire data set that supports the failedapplication must be copied to the recovery site in total before thefailed application can be executed.

BRIEF SUMMARY

This invention comprises a method, system, and article for consistentdata retrieval within an on-demand network accessible environment with ashared pool of configurable computing resources.

In one aspect, a method is provided for consistent data support for amigrated application. An application is processed at a first data sitein communication with a first data storage, which contains a primarycopy of application data to support application processing. Data isreplicated from the first data storage to backup data storage while theapplication is running. At the same time, while the data replicationprocessing is taking place, a consistency point of the application datais created. The application is migrated to a second data site havinglocal second data storage. To support a read operation, the applicationrequests consistent application data from the migrated application. Thisrequest includes receiving requested data from the second data storageif the requested data is stored in the second data storage, andreceiving transferred consistent data from the backup storage if therequested data is not stored in the second data storage.

In another aspect, a system is provided with tools to support consistentdata transfer for a migrated application. The system includes a sharedpool of configurable computer resources, and managers to support theconsistent data transfer among the resources of the shared pool. Morespecifically, an application manager is provided in the system toprocess an application at a first data site in the shared pool and incommunication with a first data storage containing a primary copy ofapplication data. In addition, a replication manager is provided incommunication with the application manager, and is responsible for datareplication from the first data storage to backup data storage in theshared pool while the application is running, including creation of aconsistency point of the application data. A migration manager isprovided to support migration of the application to a second data sitehaving local second data storage. The migration manager requestsconsistent application data to support a read operation from themigrated application. This request includes receiving requested datafrom the second data storage if data is stored in the second datastorage and receiving transferred consistent data from the backupstorage if the data is not stored in the second data storage.

In a further aspect, a computer program product is delivered as aservice through a network connection. The computer program productcomprises a computer readable storage medium having computer readableprogram code embodied therewith. Computer readable program code isprovided to process an application at a first data site in a shared poolof configurable computer resources and in communication with a firstdata storage containing a primary copy of application data. In addition,computer readable program code is provided to replicate data from thefirst data storage to backup data storage in the shared pool while theapplication is running. This data replication includes creation of aconsistency point of the application data. Computer readable programcode is also provided to migrate the application to a second data sitein the shared pool, with the second data site having local second datastorage. In addition, computer readable program code is provided torequest consistent application data to support a read operation from themigrated application. The consistent data request is supported byreceiving requested data from the second data storage if data is storedin the second data storage and receiving transferred consistent datafrom the backup storage if the data is not stored in the second datastorage.

In an even further aspect, a service is provided to support retrieval ofconsistent data. An application is processed at a first data site in ashared pool of configurable computer resources. The application is incommunication with first data storage in the pool that contains aprimary copy of application data. The service supports replicating datafrom the first data storage to a backup data storage in the shared poolwhile the application is running. This includes creation of aconsistency point of the application data in both the first data storageand the backup data storage. In addition, the service supports migratingthe application to a second data site in the shared pool, with thesecond data site having second data storage. Consistent application datais maintained by the service to support a read operation from themigrated application. The maintenance of the consistent data includesreceiving requested data from the second data storage if data is storedand receiving transferred consistent data from the backup storage if thedata is not stored in the second data storage.

Other features and advantages of this invention will become apparentfrom the following detailed description of the presently preferredembodiment of the invention, taken in conjunction with the accompanyingdrawings.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

The drawings referenced herein form a part of the specification.Features shown in the drawings are meant as illustrative of only someembodiments of the invention, and not of all embodiments of theinvention unless otherwise explicitly indicated.

FIG. 1 depicts a cloud computing node according to an embodiment of thepresent invention.

FIG. 2 depicts a cloud computing environment according to an embodimentof the present invention.

FIG. 3 depicts abstraction model layers according to an embodiment ofthe present invention.

FIG. 4 depicts a flow chart illustrating steps employed for executing anapplication and storage of write data in a system having a shared poolof configurable computer resources.

FIG. 5 depicts a flow chart illustrating the steps employed to support aplanned migration of the application in the shared pool of configurablecomputer resources.

FIG. 6 depicts a flow chart illustrating a process of an unplannedmigration of an application in the shared pool of configurable computerresources.

FIG. 7 depicts a block diagram illustrating tools embedded in a computersystem to support both planned and unplanned migration of theapplication in the shared pool of configurable computer resources.

FIG. 8 depicts is a block diagram showing a system for implementing anembodiment of the present invention.

DETAILED DESCRIPTION

It will be readily understood that the components of the presentinvention, as generally described and illustrated in the Figures herein,may be arranged and designed in a wide variety of differentconfigurations. Thus, the following detailed description of theembodiments of the apparatus, system, and method of the presentinvention, as presented in the Figures, is not intended to limit thescope of the invention, as claimed, but is merely representative ofselected embodiments of the invention.

The functional units described in this specification have been labeledas managers. A manager may be implemented in programmable hardwaredevices such as field programmable gate arrays, programmable arraylogic, programmable logic devices, or the like. The managers may also beimplemented in software for processing by various types of processors.An identified manager of executable code may, for instance, comprise oneor more physical or logical blocks of computer instructions which may,for instance, be organized as an object, procedure, function, or otherconstruct. Nevertheless, the executables of an identified manager neednot be physically located together, but may comprise disparateinstructions stored in different locations which, when joined logicallytogether, comprise the managers and achieve the stated purpose of themanagers.

Indeed, a manager of executable code could be a single instruction, ormany instructions, and may even be distributed over several differentcode segments, among different applications, and across several memorydevices. Similarly, operational data may be identified and illustratedherein within the manager, and may be embodied in any suitable form andorganized within any suitable type of data structure. The operationaldata may be collected as a single data set, or may be distributed overdifferent locations including over different storage devices, and mayexist, at least partially, as electronic signals on a system or network.

Reference throughout this specification to “a select embodiment,” “oneembodiment,” or “an embodiment” means that a particular feature,structure, or characteristic described in connection with the embodimentis included in at least one embodiment of the present invention. Thus,appearances of the phrases “a select embodiment,” “in one embodiment,”or “in an embodiment” in various places throughout this specificationare not necessarily referring to the same embodiment.

Furthermore, the described features, structures, or characteristics maybe combined in any suitable manner in one or more embodiments. In thefollowing description, numerous specific details are provided, such asexamples of an application manager, a replication manager, a migrationmanager, etc., to provide a thorough understanding of embodiments of theinvention. One skilled in the relevant art will recognize, however, thatthe invention can be practiced without one or more of the specificdetails, or with other methods, components, materials, etc. In otherinstances, well-known structures, materials, or operations are not shownor described in detail to avoid obscuring aspects of the invention.

The illustrated embodiments of the invention will be best understood byreference to the drawings, wherein like parts are designated by likenumerals throughout. The following description is intended only by wayof example, and simply illustrates certain selected embodiments ofdevices, systems, and processes that are consistent with the inventionas claimed herein.

A cloud computing environment is service oriented with a focus onstatelessness, low coupling, modularity, and semantic interoperability.At the heart of cloud computing is an infrastructure comprising anetwork of interconnected nodes. Referring now to FIG. 1, a schematic ofan example of a cloud computing node is shown. Cloud computing node (10)is only one example of a suitable cloud computing node and is notintended to suggest any limitation as to the scope of use orfunctionality of embodiments of the invention described herein.Regardless, cloud computing node (10) is capable of being implementedand/or performing any of the functionality set forth hereinabove. Incloud computing node (10) there is a computer system/server (12), whichis operational with numerous other general purpose or special purposecomputing system environments or configurations. Examples of well-knowncomputing systems, environments, and/or configurations that may besuitable for use with computer system/server (12) include, but are notlimited to, personal computer systems, server computer systems, thinclients, thick clients, hand-held or laptop devices, multiprocessorsystems, microprocessor-based systems, set top boxes, programmableconsumer electronics, network PCs, minicomputer systems, mainframecomputer systems, and distributed cloud computing environments thatinclude any of the above systems or devices, and the like.

Computer system/server (12) may be described in the general context ofcomputer system-executable instructions, such as program modules, beingexecuted by a computer system. Generally, program modules may includeroutines, programs, objects, components, logic, data structures, and soon that perform particular tasks or implement particular abstract datatypes. Computer system/server (12) may be practiced in distributed cloudcomputing environments where tasks are performed by remote processingdevices that are linked through a communications network. In adistributed cloud computing environment, program modules may be locatedin both local and remote computer system storage media including memorystorage devices.

As shown in FIG. 1, computer system/server (12) in cloud computing node(10) is shown in the form of a general-purpose computing device. Thecomponents of computer system/server (12) may include, but are notlimited to, one or more processors or processing units (16), a systemmemory (28), and a bus (18) that couples various system componentsincluding system memory (28) to processor (16). Bus (18) represents oneor more of any of several types of bus structures, including a memorybus or memory controller, a peripheral bus, an accelerated graphicsport, and a processor or local bus using any of a variety of busarchitectures. By way of example, and not limitation, such architecturesinclude Industry Standard Architecture (ISA) bus, Micro ChannelArchitecture (MCA) bus, Enhanced ISA (EISA) bus, Video ElectronicsStandards Association (VESA) local bus, and Peripheral ComponentInterconnects (PCI) bus. Computer system/server (12) typically includesa variety of computer system readable media. Such media may be anyavailable media that is accessible by computer system/server (12), andit includes both volatile and non-volatile media, removable andnon-removable media.

System memory (28) can include computer system readable media in theform of volatile memory, such as random access memory (RAM) (30) and/orcache memory (32). Computer system/server (12) may further include otherremovable/non-removable, volatile/non-volatile computer system storagemedia. By way of example only, storage system (34) can be provided forreading from and writing to a non-removable, non-volatile magnetic media(not shown and typically called a “hard drive”). Although not shown, amagnetic disk drive for reading from and writing to a removable,non-volatile magnetic disk (e.g., a “floppy disk”), and an optical diskdrive for reading from or writing to a removable, non-volatile opticaldisk such as a CD-ROM, DVD-ROM or other optical media can be provided.In such instances, each can be connected to bus (18) by one or more datamedia interfaces. As will be further depicted and described below,memory (28) may include at least one program product having a set (e.g.,at least one) of program modules that are configured to carry out thefunctions of embodiments of the invention.

Program/utility (40), having a set (at least one) of program modules(42), may be stored in memory (28) by way of example, and notlimitation, as well as an operating system, one or more applicationprograms, other program modules, and program data. Each of the operatingsystems, one or more application programs, other program modules, andprogram data or some combination thereof, may include an implementationof a networking environment. Program modules (42) generally carry outthe functions and/or methodologies of embodiments of the invention asdescribed herein.

Computer system/server (12) may also communicate with one or moreexternal devices (14), such as a keyboard, a pointing device, a display(24), etc.; one or more devices that enable a user to interact withcomputer system/server (12); and/or any devices (e.g., network card,modem, etc.) that enable computer system/server (12) to communicate withone or more other computing devices. Such communication can occur viaInput/Output (I/O) interfaces (22). Still yet, computer system/server(12) can communicate with one or more networks such as a local areanetwork (LAN), a general wide area network (WAN), and/or a publicnetwork (e.g., the Internet) via network adapter (20). As depicted,network adapter (20) communicates with the other components of computersystem/server (12) via bus (18). It should be understood that althoughnot shown, other hardware and/or software components could be used inconjunction with computer system/server (12). Examples, include, but arenot limited to: microcode, device drivers, redundant processing units,external disk drive arrays, RAID systems, tape drives, and data archivalstorage systems, etc.

Referring now to FIG. 2, illustrative cloud computing environment (50)is depicted. As shown, cloud computing environment (50) comprises one ormore cloud computing nodes (10) with which local computing devices usedby cloud consumers, such as, for example, personal digital assistant(PDA) or cellular telephone (54A), desktop computer (54B), laptopcomputer (54C), and/or automobile computer system (54N) may communicate.Nodes (10) may communicate with one another. They may be grouped (notshown) physically or virtually, in one or more networks, such asPrivate, Community, Public, or Hybrid clouds as described hereinabove,or a combination thereof. This allows cloud computing environment (50)to offer infrastructure, platforms and/or software as services for whicha cloud consumer does not need to maintain resources on a localcomputing device. It is understood that the types of computing devices(54A)-(54N) shown in FIG. 2 are intended to be illustrative only andthat computing nodes (10) and cloud computing environment (50) cancommunicate with any type of computerized device over any type ofnetwork and/or network addressable connection (e.g., using a webbrowser).

Referring now to FIG. 3, a set of functional abstraction layers providedby cloud computing environment (50) (FIG. 2) is shown. It should beunderstood in advance that the components, layers, and functions shownin FIG. 3 are intended to be illustrative only and embodiments of theinvention are not limited thereto. As depicted, the following layers andcorresponding functions are provided: hardware and software layer (60),virtualization layer (62), management layer (64), and workload layer(66). The hardware and software layer (60) includes hardware andsoftware components. Examples of hardware components include mainframes,in one example IBM® zSeries® systems; RISC (Reduced Instruction SetComputer) architecture based servers, in one example IBM pSeries®systems; IBM xSeries® systems; IBM BladeCenter® systems; storagedevices; networks and networking components. Examples of softwarecomponents include network application server software, in one exampleIBM WebSphere® application server software; and database software, inone example IBM DB2® database software. (IBM, zSeries, pSeries, xSeries,BladeCenter, WebSphere, and DB2 are trademarks of International BusinessMachines Corporation registered in many jurisdictions worldwide).

Virtualization layer (62) provides an abstraction layer from which thefollowing examples of virtual entities may be provided: virtual servers;virtual storage; virtual networks, including virtual private networks;virtual applications and operating systems; and virtual clients.

In one example, management layer (64) may provide the followingfunctions: resource provisioning, metering and pricing, user portal,service level management, and SLA planning and fulfillment. Thefunctions are described below. Resource provisioning provides dynamicprocurement of computing resources and other resources that are utilizedto perform tasks within the cloud computing environment. Metering andpricing provides cost tracking as resources are utilized within thecloud computing environment, and billing or invoicing for consumption ofthese resources. In one example, these resources may compriseapplication software licenses. Security provides identity verificationfor cloud consumers and tasks, as well as protection for data and otherresources. User portal provides access to the cloud computingenvironment for consumers and system administrators. Service levelmanagement provides cloud computing resource allocation and managementsuch that required service levels are met. Service Level Agreement (SLA)planning and fulfillment provides pre-arrangement for, and procurementof, cloud computing resources for which a future requirement isanticipated in accordance with an SLA.

Workloads layer (66) provides examples of functionality for which thecloud computing environment may be utilized. Examples of workloads andfunctions which may be provided from this layer includes, but is notlimited to: mapping and navigation; software development and lifecyclemanagement; virtual classroom education delivery; data analyticsprocessing; operation processing; and maintenance of consistentapplication data to support migration within the cloud computingenvironment.

In the shared pool of configurable computer resources described herein,hereinafter referred to as a cloud computing environment, applicationsmay migrate to any data center, also referred to herein as a data site.There are two general scenarios in which an application is subject tomigration, including a planned migration and an unplanned migration. Ina planned migration, the application migrates to any data center in thecloud while maintaining disaster recovery support, and in an unplannedmigration, the application is subject to failure and recovers in anydata center in the cloud while maintaining disaster recovery support.Accordingly, the difference between a planned migration and an unplannedmigration is the failure and subsequent recovery of a failedapplication.

Regardless of the planned or unplanned form of migration, bothcategories of migration require a minimum amount of ‘critical’ data tobe transferred and cached to support application execution. All other‘non-critical’ data is asynchronously cached in the background so as notto interfere with running applications. FIG. 4 is a flow chart (400)illustrating steps employed for executing an application and storage ofwrite data in the shared pool of configurable computer resources,hereinafter referred to as a cloud. Specifically, an application runs ata data center in the cloud (402). The application may support readand/or write operations. Data generated from a write operation is storedin data storage local to the data center in which the application isprocessing, e.g. local storage (404). At the same time, the data createdfrom the write operation is replicated from the local data storage tobackup data storage at a remote data center while the applicationcontinues to process one or more operations (406). Accordingly, theprocess of storing and replicating write operation data, shown herein,supports disaster recovery of application data by replicating operationdata from the local data storage to the backup data storage.

There are two scenarios in which an application may be subject tomigration from a first data center in the cloud to a second data centerin the cloud. These include a planned migration and an unplannedmigration. FIG. 5 is a flow chart (500) illustrating the steps employedto support a planned migration of the application from a first datacenter to a second data center in the cloud computing environment. Anapplication runs at a first data center in the cloud (502). Theapplication may support read and/or write operations. Data generatedfrom a write operation is stored in data storage local to the first datacenter in which the application is processing, e.g. local storage (504).At the same time, the data created from the write operation isreplicated from the local data storage to backup data storage at aremote data center while the application continues to process one ormore operations (506). The replication at step (506) includes both dataand metadata from the write operation. The replication at step (506) maybe conducted synchronously or asynchronously from one or more servernodes in the first data center to one or more server nodes in the backupdata storage. Regardless of the format of the replication at step (506),a data consistency point is created on both the local and backup datastorage. The creation of the consistency point ensures that should theapplication be subject to a failure, the application can recover from aconsistent data set. A consistency point can be achieved using severaldifferent methods known to someone skilled in the art. In oneembodiment, a file system or storage system snapshot is taken andcopy-on-write semantics are employed to save data at a certain point intime without delaying application requests for an extended period oftime. In one embodiment, any level of consistency can be used,including, but not limited to, application, crash, file system, etc.Accordingly, data and metadata from one or more write operations arestored in local data storage and replicated to backup data storage, withcreation of one or more consistency points in both data storagelocations.

For a planned application migration, the application is quiesced andexecution is suspended (508) at the first data center prior to migrationand a consistency point is created (510). Following step (510), a seconddata center separate from the first data center is selected (512), andthe application is migrated to the selected second data center (514).Following migration of the application at step (514), the application isunquiesced and re-launched at the second data center (516), and data istransferred from the backup data storage to data storage local to thesecond data center (518). Although the application can process readoperations with data from the backup data storage, it is more efficientto process the operations from local data storage.

Once the application is re-launched it can support both read and writeoperations. When the application initiates operation processing (520),it is determined if the operation is a read operation or a writeoperation (522). Following determination of a read operation (524), itis further determined if the data byte-range or file system metadata tosupport the operation has already been transferred from the backup datastorage (526). If at step (526) it is determined that the data ormetadata exists in the local data storage, the data is returned to theapplication to support the read operation (528). Conversely, if at step(526) it is determined that the data or metadata is not present in thelocal data storage, data and/or metadata to support the read operationis transferred from the backup data storage to the second data storagelocal to the migrated application (530), followed by a return to step(528) where the data is returned to the application to support the readoperation. In the interim, transfer of data from the backup storage tothe second data storage continues (532). Accordingly, as shown hereindata and/or metadata to support a read operation is initially sought atlocal data storage, and if not present, from backup data storage at aremote location.

Steps (522)-(528) demonstrate processing of a read operation for amigrated application. In addition to read operations, the applicationmay also support and process write operations. Following a determinationof a write operation (534), the application stores write data at thesecond data storage (536). As shown in FIG. 4, data is replicated fromlocal storage to backup storage prior to migration. For a migratedapplication, the data replication to the backup storage takes place aswell, but only for data that has not been previously replicated to thebackup storage. Following step (536), it is determined if the write datagenerated by the application has been previously replicated to thebackup storage (538). A negative response to the determination at step(538) is followed by replication of the generated and non-previouslyreplicated write data to the backup storage (540). However, a positiveresponse to the determination at step (538) is an indication that thegenerated write data is a duplicate of previously replicated data, andas such, the generated write data is not flushed to the backup storage(542). Accordingly, the process of writing data to local storage andreplicating the data to the backup storage is a closed loop data storageand replication system.

As described above, migration of an application across data centers maybe planned or unplanned. FIG. 5 illustrates the process of a plannedapplication migration. FIG. 6 is a flow chart (600) illustrating aprocess of an unplanned migration of an application from a first datacenter to a second data center. An application runs at a first datacenter in the cloud (602). The application may support read and/or writeoperations. Data generated from a write operation is stored in datastorage local to the first data center in which the application isprocessing, e.g. local storage (604). At the same time, the data createdfrom the write operation is replicated from the local data storage tobackup data storage at a remote data center while the applicationcontinues to process one or more operations (606). The replication atstep (606) includes both data and metadata from the write operation. Thereplication at step (606) may be conducted synchronously orasynchronously from one or more server nodes in the first data center toone or more server nodes in the backup data storage. Regardless of theformat of the replication at step (606), a consistency point is createdon both local and backup data storage (608). The creation of theconsistency points ensures that should the application be subject to afailure, the application can recover from a consistent data set. In oneembodiment, any level of consistency can be used, including, but notlimited to, application, crash, file system, etc. There are differenttechniques that may be employed to create the consistent data set,including, but not limited to restoring a previous snapshot of the dataset. Accordingly, data and metadata from one or more write operationsare stored in local data storage and replicated to backup data storage,with creation of one or more consistency points in both data storagelocations.

For an unplanned application migration, there is no quiescing of theapplication or suspension of application execution. Rather, an unplannedapplication migration follows an unexpected failure of the hardwarelocal to the first data center (610). In one embodiment, the hardwarefailure may be the local data storage of the first data center. Prior tomigration of the application to a different data center, a second datacenter separate from the first data center is selected for migration(612) and the application is re-launched in the selected second datacenter (614). Accordingly, in a planned migration, the applicationaffected by the hardware failure is re-launch at a different datacenter.

Once the migration is completed, the application is re-launched at thesecond data center (616). In one embodiment, the saved consistency pointis restored so that the associated dataset can be accessed and modifiedby the second storage system of the second data center. Following there-launch at step (616), data is transferred from the backup datastorage to data storage local to the second data center (618). The datatransfer at step (618) is from a saved consistency point in the backupdata storage. Although the application can process read operations withdata from the backup data storage, it is more efficient to process theoperations from local data storage. The re-launched application cansupport both read and write operations. When the application initiatesoperation processing (620), it is determined if the operation is a readoperation or a write operation (622). Following determination of a readoperation (624), it is determined if the data byte-range or file systemmetadata to support the operation has already been transferred from thebackup data storage (626). If at step (626) it is determined that thedata or metadata exists in the local data storage, the data is returnedto the application to support the read operation (628). Conversely, ifat step (626) it is determined that the data or metadata is not presentin the local data storage, data and/or metadata to support the readoperation is transferred from the backup data storage to the second datastorage local to the migrated application (630), followed by a return tostep (628) where the data is returned to the application to support theread operation. In the interim transfer of data from the backup storageto the second data storage continues (632). Accordingly, as shown hereindata and/or metadata to support a read operation is initially sought atlocal data storage, and if not present, from backup data storage at aremote location.

However, following determination of a write operation (634), theapplication stores write data at the second data storage (636). As shownin FIG. 4, data is replicated from local storage to backup storage priorto migration. For a migrated application, the data replication to thebackup storage takes place as well, but only for data that has not beenpreviously replicated to the backup storage. Following step (636), it isdetermined if the write data generated by the application has beenpreviously replicated to the backup storage (638). A negative responseto the determination at step (638) is followed by replication of thegenerated and non-previously replicated write data to the backup storage(640). However, a positive response to the determination at step (638)is an indication that the generated write data is a duplicate ofpreviously replicated data, and as such, the generated write data is notflushed to the backup storage (642). Accordingly, the process of writingdata to local storage and replicating the data to the backup storage isa closed loop data storage and replication system.

As demonstrated in the flow charts of FIGS. 4-6, a method is employed tosupport planned and unplanned migration of an application from a firstdata center to a second data center, both forms of migration supportedmaintaining disaster recovery support through creation of one or moreconsistency points on the backup data storage. Similarly, following theconclusion of either of the planned migration or unplanned migrationillustrated in FIGS. 5 and 6, respectively, application processingcontinues with data replication and creation of consistency points. FIG.7 is a block diagram (700) illustrating tools embedded in a computersystem to support both planned and unplanned migration of theapplication across data centers. More specifically, a shared pool ofconfigurable computer resources is shown with a first data center (710),a second data center (730), and a third data center (750). In oneembodiment, the third data center (750) may be referred to as a backupdata center. Although three data centers are shown in the exampleherein, the invention should not be limited to this quantity of datacenters in the computer system. Accordingly, three or more data centersmay be employed to support dynamic application migration.

Each of the data centers in the system is provided with at least oneserver in communication with data storage. More specifically, the firstdata center (710) is provided with a server (720) having a processingunit (722), in communication with memory (724) across a bus (726), andin communication with first local storage (728); the second data center(730) is provided with a server (740) having a processing unit (742), incommunication with memory (744) across a bus (746), and in communicationwith second local storage (748); the third data center (750) is providedwith a server (760) having a processing unit (762), in communicationwith memory (764) across a bus (766), and in communication with thirdlocal storage (768). Both server (720) and server (740) may separatelycommunicate with the third local storage (768) across a networkconnection (705).

In the example shown herein, an application (790) processes read andwrite operations local to the first data center (710). Read operationsare supported with data in the first local storage (728), and if thedata is not present therein, with data in the third local storage (768).Similarly, data from write operations are written to the first localstorage (728), and non-duplicate data is replicated to the third localstorage (768). Several tools are provided to support both planned andunplanned migration of the application from the first data center (710)to the second data center (730). More specifically, an applicationmanager (780) is provided to process the application (790) at the firstdata center (710) in the shared pool. The application manager (780)communicates with a replication manager (782). More specifically, thereplication manager (782) replicates data from the first local storage(728) to the third local storage (768) in the shared pool while theapplication (790) is running. As described above to support both plannedand unplanned migration, one or more consistency points must bemaintained in both the first and third local storage (728) and (768),respectively. The replication manager (782) is responsible for creationof one or more consistency points of the application data in both thefirst local storage (728) and the third local storage (768).Furthermore, the replication manager supports either synchronous orasynchronous replication of data in the cloud environment. Accordingly,the replication manager (782) communicates with the application manager(780) to manage and support creation of consistency points in the storeddata.

In addition to the application and replication managers, (780) and (782)respectively, a a migration manager (784) is provided to migrate theapplication from the first data center (710) to the second data center(720). The migration manager (784) plans migration of the application(790), including quiescing the application (790) and suspendingexecution of the application (790) prior to migration to the second datacenter (730), and unquiescing the application (790) following completionof the migration to the second data center (730). As shown, the seconddata center (730) is separate from the first data center (710). Themigration manager (784) communicates with both the application manager(780) and the replication manager (782). More specifically, themigration manager (784) requests consistent application data to supporta read operation from the migrated application (790), includingreceiving requested data from the second local storage (748) if data ispresent and receiving transferred consistent data from the third localstorage (768) if the data is not present in the second local storage(748). To support the consistent data request, the migration manager(784) checks either a data byte range or file system metadata, andfurther mitigates transfer of replicated data. The transfer limits areapplied to both ensure that data is replicated only one time as well aslimit transfer of the consistent data to a single transfer. Accordingly,a consistent state of the data is maintained across the first and seconddata centers, (710) and (730) respectively, to allow failover.

As shown herein, migration of the application (790) is supported by theapplication, replication, and migration managers, (780), (782), and(784) respectively, for both planned and unplanned migration scenarios.In one embodiment, an unplanned migration scenario occurs in response toa failure of a processing element at the first data center (710) andrecovery of the processing element. Tools are provided in the sharedpool of configurable computer resources, i.e. cloud, to restore theprocessing element from a saved consistency point prior to execution ofthe processing element. As described above, the processing element maybe an application executing on the processing unit (722). However, theinvention should not be limited to an application. In one embodiment,the processing element may be a virtual machine operating in the datacenter.

As identified above, the application, replication, and migrationmanagers, (780), (782), and (784) respectively, are shown residing inmemory (724) of the server (720) local to the first data center (710).Although in one embodiment, the application, replication, and migrationmanagers, (780), (782), and (784) respectively, may reside as hardwaretools external to memory (724) of server (720), or they may beimplemented as a combination of hardware and software. Similarly, in oneembodiment, the managers may be combined into a single functional itemthat incorporates the functionality of the separate items. As shownherein, each of the manager(s) are shown local to one data center.However, in one embodiment they may be collectively or individuallydistributed across the shared pool of configurable computer resourcesand function as a unit to manage dynamic application migration withdisaster recovery support. Accordingly, the managers may be implementedas software tools, hardware tools, or a combination of software andhardware tools.

As will be appreciated by one skilled in the art, aspects of the presentinvention may be embodied as a system, method or computer programproduct. Accordingly, aspects of the present invention may take the formof an entirely hardware embodiment, an entirely software embodiment(including firmware, resident software, micro-code, etc.) or anembodiment combining software and hardware aspects that may allgenerally be referred to herein as a “circuit,” “module” or “system.”Furthermore, aspects of the present invention may take the form of acomputer program product embodied in one or more computer readablemedium(s) having computer readable program code embodied thereon.

Any combination of one or more computer readable medium(s) may beutilized. The computer readable medium may be a computer readable signalmedium or a computer readable storage medium. A computer readablestorage medium may be, for example, but not limited to, an electronic,magnetic, optical, electromagnetic, infrared, or semiconductor system,apparatus, or device, or any suitable combination of the foregoing. Morespecific examples (a non-exhaustive list) of the computer readablestorage medium would include the following: an electrical connectionhaving one or more wires, a portable computer diskette, a hard disk, arandom access memory (RAM), a read-only memory (ROM), an erasableprogrammable read-only memory (EPROM or Flash memory), an optical fiber,a portable compact disc read-only memory (CD-ROM), an optical storagedevice, a magnetic storage device, or any suitable combination of theforegoing. In the context of this document, a computer readable storagemedium may be any tangible medium that can contain, or store a programfor use by or in connection with an instruction execution system,apparatus, or device.

A computer readable signal medium may include a propagated data signalwith computer readable program code embodied therein, for example, inbaseband or as part of a carrier wave. Such a propagated signal may takeany of a variety of forms, including, but not limited to,electro-magnetic, optical, or any suitable combination thereof. Acomputer readable signal medium may be any computer readable medium thatis not a computer readable storage medium and that can communicate,propagate, or transport a program for use by or in connection with aninstruction execution system, apparatus, or device.

Program code embodied on a computer readable medium may be transmittedusing any appropriate medium, including but not limited to wireless,wireline, optical fiber cable, RF, etc., or any suitable combination ofthe foregoing.

Computer program code for carrying out operations for aspects of thepresent invention may be written in any combination of one or moreprogramming languages, including an object oriented programming languagesuch as Java, Smalltalk, C++ or the like and conventional proceduralprogramming languages, such as the “C” programming language or similarprogramming languages. The program code may execute entirely on theuser's computer, partly on the user's computer, as a stand-alonesoftware package, partly on the user's computer and partly on a remotecomputer or entirely on the remote computer or server. In the latterscenario, the remote computer may be connected to the user's computerthrough any type of network, including a local area network (LAN) or awide area network (WAN), or the connection may be made to an externalcomputer (for example, through the Internet using an Internet ServiceProvider).

Aspects of the present invention are described above with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems) and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer program instructions. These computer program instructions maybe provided to a processor of a general purpose computer, specialpurpose computer, or other programmable data processing apparatus toproduce a machine, such that the instructions, which execute via theprocessor of the computer or other programmable data processingapparatus, create means for implementing the functions/acts specified inthe flowchart and/or block diagram block or blocks.

These computer program instructions may also be stored in a computerreadable medium that can direct a computer, other programmable dataprocessing apparatus, or other devices to function in a particularmanner, such that the instructions stored in the computer readablemedium produce an article of manufacture including instructions whichimplement the function/act specified in the flowchart and/or blockdiagram block or blocks.

The computer program instructions may also be loaded onto a computer,other programmable data processing apparatus, or other devices to causea series of operational steps to be performed on the computer, otherprogrammable apparatus or other devices to produce a computerimplemented process such that the instructions which execute on thecomputer or other programmable apparatus provide processes forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks.

Referring now to FIG. 8 is a block diagram (800) showing a system forimplementing an embodiment of the present invention. The computer systemincludes one or more processors, such as a processor (802). Theprocessor (802) is connected to a communication infrastructure (804)(e.g., a communications bus, cross-over bar, or network). The computersystem can include a display interface (806) that forwards graphics,text, and other data from the communication infrastructure (804) (orfrom a frame buffer not shown) for display on a display unit (808). Thecomputer system also includes a main memory (810), preferably randomaccess memory (RAM), and may also include a secondary memory (812). Thesecondary memory (812) may include, for example, a hard disk drive (814)and/or a removable storage drive (816), representing, for example, afloppy disk drive, a magnetic tape drive, or an optical disk drive. Theremovable storage drive (816) reads from and/or writes to a removablestorage unit (818) in a manner well known to those having ordinary skillin the art. Removable storage unit (818) represents, for example, afloppy disk, a compact disc, a magnetic tape, or an optical disk, etc.,which is read by and written to by removable storage drive (816). Aswill be appreciated, the removable storage unit (818) includes acomputer readable medium having stored therein computer software and/ordata.

In alternative embodiments, the secondary memory (812) may include othersimilar means for allowing computer programs or other instructions to beloaded into the computer system. Such means may include, for example, aremovable storage unit (820) and an interface (822). Examples of suchmeans may include a program package and package interface (such as thatfound in video game devices), a removable memory chip (such as an EPROM,or PROM) and associated socket, and other removable storage units (820)and interfaces (822) which allow software and data to be transferredfrom the removable storage unit (820) to the computer system.

The computer system may also include a communications interface (824).Communications interface (824) allows software and data to betransferred between the computer system and external devices. Examplesof communications interface (824) may include a modem, a networkinterface (such as an Ethernet card), a communications port, or a PCMCIAslot and card, etc. Software and data transferred via communicationsinterface (824) are in the form of signals which may be, for example,electronic, electromagnetic, optical, or other signals capable of beingreceived by communications interface (824). These signals are providedto communications interface (824) via a communications path (i.e.,channel) (826). This communications path (826) carries signals and maybe implemented using wire or cable, fiber optics, a phone line, acellular phone link, a radio frequency (RF) link, and/or othercommunication channels.

In this document, the terms “computer program medium,” “computer usablemedium,” and “computer readable medium” are used to generally refer tomedia such as main memory (810) and secondary memory (812), removablestorage drive (816), and a hard disk installed in hard disk drive (814).

Computer programs (also called computer control logic) are stored inmain memory (810) and/or secondary memory (812). Computer programs mayalso be received via a communication interface (824). Such computerprograms, when run, enable the computer system to perform the featuresof the present invention as discussed herein. In particular, thecomputer programs, when run, enable the processor (802) to perform thefeatures of the computer system. Accordingly, such computer programsrepresent controllers of the computer system.

The flowcharts and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowcharts or block diagrams may represent a module, segment, or portionof code, which comprises one or more executable instructions forimplementing the specified logical function(s). It should also be notedthat, in some alternative implementations, the functions noted in theblock may occur out of the order noted in the figures. For example, twoblocks shown in succession may, in fact, be executed substantiallyconcurrently, or the blocks may sometimes be executed in the reverseorder, depending upon the functionality involved. It will also be notedthat each block of the block diagrams and/or flowchart illustration, andcombinations of blocks in the block diagrams and/or flowchartillustration, can be implemented by special purpose hardware-basedsystems that perform the specified functions or acts, or combinations ofspecial purpose hardware and computer instructions.

The terminology used herein is for the purpose of describing particularembodiments only and is not intended to be limiting of the invention. Asused herein, the singular forms “a”, “an” and “the” are intended toinclude the plural forms as well, unless the context clearly indicatesotherwise. It will be further understood that the terms “comprises”and/or “comprising,” when used in this specification, specify thepresence of stated features, integers, steps, operations, elements,and/or components, but do not preclude the presence or addition of oneor more other features, integers, steps, operations, elements,components, and/or groups thereof.

The corresponding structures, materials, acts, and equivalents of allmeans or step plus function elements in the claims below are intended toinclude any structure, material, or act for performing the function incombination with other claimed elements as specifically claimed. Thedescription of the present invention has been presented for purposes ofillustration and description, but is not intended to be exhaustive orlimited to the invention in the form disclosed. Many modifications andvariations will be apparent to those of ordinary skill in the artwithout departing from the scope and spirit of the invention. Theembodiment was chosen and described in order to best explain theprinciples of the invention and the practical application, and to enableothers of ordinary skill in the art to understand the invention forvarious embodiments with various modifications as are suited to theparticular use contemplated. Accordingly, the enhanced cloud computingmodel supports flexibility with respect to application processing anddisaster recovery, including, but not limited to, supporting separationof the location of the data from the application location and selectionof an appropriate recovery site.

Alternative Embodiment

It will be appreciated that, although specific embodiments of theinvention have been described herein for purposes of illustration,various modifications may be made without departing from the spirit andscope of the invention. In particular, the system can be configured tosupport planned and unplanned migration of a virtual machine operatingat the first data center. The virtual machine needs to ensure that aconsistent and usable data set is transferred to the third data centeras backup data storage. To recover a virtual machine from a failed datacenter, a virtual machine restore from a saved consistency point isperformed on a data set prior to the virtual machine execution.Accordingly, the scope of protection of this invention is limited onlyby the following claims and their equivalents.

1. A method comprising: processing an application at a first data siteand in communication with a first data storage containing a primary copyof application data; replicating data from the first data storage to abackup data storage while the application is running, including creatinga consistency point of the application data in both the first datastorage and the backup data storage; migrating the application to asecond data site having local second data storage; and requestingconsistent application data to support a read operation from themigrated application, including receiving requested data from the seconddata storage if data is stored in the second data storage and receivingtransferred consistent data from the backup storage if the data is notstored in the second data storage.
 2. The method of claim 1, furthercomprising a failure of a processing element at the first data site andrecovery of the processing element, including restoring the processingelement from a saved consistency point prior to execution of theprocessing element.
 3. The method of claim 2, wherein the processingelement is selected from the group consisting of: a virtual machine andthe processing application.
 4. The method of claim 2, further comprisingsoftware to support recovery of the processing element in a cloudcomputing environment.
 5. The method of claim 1, wherein replication ofdata is performed synchronously or asynchronously.
 6. The method ofclaim 1, further comprising planning migration of the application,including quiescing the application and suspending execution of theapplication prior to migration to the second data site.
 7. The method ofclaim 1, wherein requesting consistent data to support the readoperation includes checking an item selected from the group consistingof: a data byte range and file system metadata.
 8. The method of claim1, further comprising writing data from the migrated application to thesecond data storage and replicating non-previously replicated write datafrom the second data storage to the backup storage.
 9. A systemcomprising: a shared pool of configurable computer resources; anapplication manager to process an application at a first data site inthe shared pool and in communication with a first data storagecontaining a primary copy of application data; a replication manager incommunication with the application manager, the replication manager toreplicate data from the first data storage to a backup data storage inthe shared pool while the application is running, including creation ofa consistency point of the application data in both the first datastorage and the backup data storage; a migration manager to migrate theapplication to a second data site having local second data storage; andthe migration manager to request consistent application data to supporta read operation from the migrated application, including receivingrequested data from the second data storage if data is stored in thesecond data storage and receiving transferred consistent data from thebackup storage if the data is not stored in the second data storage. 10.The system of claim 9, further comprising a failure of a processingelement at the first data site and recovery of the processing element,including providing software in a cloud environment to restore theprocessing element from a saved consistency point prior to execution ofthe processing element.
 11. The system of claim 10, wherein themigration manager requesting consistent data to support the readoperation includes checking an item selected from the group consistingof: a data byte range and file system metadata.
 12. The system of claim10, further comprising the migration manager to limit transfer ofreplicated data, including limit transfer of the consistent data to asingle transfer.
 13. The system of claim 9, wherein replication of datais performed by the replication manager synchronously or asynchronously.14. The system of claim 9, further comprising the migration manager toplan migration of the application, including the migration manager toquiesce the application and to suspend execution of the applicationprior to migration to the second data site.
 15. A computer programdelivered as a service through a network connection, the computerprogram product comprising a computer readable storage medium havingcomputer readable program code embodied therewith, the computer readableprogram code comprising: computer readable program code configured toprocess an application at a first data site in a shared pool ofconfigurable computer resources and in communication with a first datastorage containing a primary copy of application data; computer readableprogram code configured to replicate data from the first data storage toa backup data storage in the shared pool while the application isrunning, including creation of a consistency point of the applicationdata in both the first data storage and the backup data storage;computer readable program code configured to migrate the application toa second data site in the shared pool having local second data storage;and computer readable program code configured to request consistentapplication data to support a read operation from the migratedapplication, including receiving requested data from the second datastorage if data is stored in the second data storage and receivingtransferred consistent data from the backup storage if the data is notstored in the second data storage.
 16. The computer program product ofclaim 15, further comprising code configured to restore a failedprocessing element at the first data site and to support recovery of theprocessing element, including restoring the processing element from asaved consistency point prior to execution of the processing element,wherein the processing element is selected from the group consisting of:a virtual machine and the processing application.
 17. The computerprogram product of claim 16, wherein the code to request consistent datato support the read operation includes checking an item selected fromthe group consisting of: a data byte range and file system metadata. 18.The computer program product of claim 15, wherein replication of data isperformed by the replication code synchronously or asynchronously. 19.The computer program product of claim 15, further comprising the code toplan migration of the application, including the code to quiesce theapplication and to suspend execution of the application prior tomigration to the second data site.
 20. A service to support retrieval ofconsistent data, comprising: processing an application at a first datasite in a shared pool of configurable computer resources and incommunication with a first data storage in the pool and containing aprimary copy of application data; replicating data from the first datastorage to a backup data storage in the shared pool while theapplication is running, including creation of a consistency point of theapplication data in both the first data storage and the backup datastorage; migrating the application to a second data site in the sharedpool having second data storage; and consistent application data tosupport a read operation from the migrated application, includingreceiving requested data from the second data storage if data is storedand receiving transferred consistent data from the backup storage if thedata is not stored in the second data storage.